Pinging @elastic/response-ops (Team:ResponseOps)

@mdefazio @MichaelMarcialis @kyrspl

I was looking for pattern guidance on this and found this issue #195048.
I saw the conclusions there, but what would you recommend to do in this case?

All fields inside Add comment in case section are optional, and the idea was to add the label (optional) to the title, as @adcoelho mentioned, since we are using the labelAppend as Add variable link.

Can you give me a recommendation here for consistency's sake?

Rather than adding "(optional)" text, my first instinct here would be to change the "Add comment in case" header to a togglable element, like an EuiSwitch. When the switch is off, all of the form elements in that section are hidden. When the switch is on, all of the form elements in that section are visible. The assumption then would be that if the switch is on and the form elements are visible, then they are all required.

It's a good idea @MichaelMarcialis and makes a lot of sense in this flow.

@adcoelho as agreed, please substitute the header to an EuiSwitch. Should look like this (same for the edit flow):

Feel free to merge this as an interim version and add the toggle version later on.

cc: @cnasikas

@elasticmachine merge upstream

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7670afa

Failed CI Steps

• Jest Integration Tests elastic/search-team#4

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

History

• 💛 Build #231459 was flaky 9facf96

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @adcoelho